-
WORD Research this...2 Chronicles 8
- 1 Da de tyve Aar var omme, i hvilke Salomo havde bygget paa HERRENS Hus og sit Palads —
- 2 ogsaa de Byer, Huram afstod til Salomo, befæstede Salomo og lod Israeliterne bosætte sig i dem —
- 3 drog Salomo til Hamat-Zoba og indtog det.
- 4 Han befæstede ogsaa Tadmor i Ørkenen og alle de Forraadsbyer, han byggede i Hamat;
- 5 ligeledes genopbyggede han Øvre— og Nedre-Bet-Horon, saa de blev Fæstninger med Mure, Porte og Portslaaer,
- 6 ligeledes Ba'alat og alle Salomos Forraadsbyer, Vognbyerne og Rytterbyerne, og alt andet, som Salomo fik Lyst til at bygge i Jerusalem, i Libanon og i hele sit Rige.
- 7 Alt, hvad der var tilbage af Hetiterne, Amoriterne, Perizziterne, Hivviterne og Jebusiterne, og som ikke hørte til Israeliterne,
- 8 deres Efterkommere, som var tilbage efter dem i Landet, og som Israeliterne ikke havde tilintetgjort, dem udskrev Salomo til Hoveriarbejde, som det er den Dag i Dag.
- 9 Af Israeliterne derimod gjorde Salomo ingen til Arbejdstrælle for sig, men de var Krigsfolk, Hærførere og Vognkæmpere hos ham og Førere for hans Stridsvogne og Rytteri.
- 10 Tallet paa Kong Salomos Overfogeder var 250; de havde Tilsyn med Folkene.
- 11 Faraos Datter flyttede Salomo fra Davidsbyen ind i det Hus, han havde bygget til hende; thi han tænkte: »Jeg vil ikke have en Kvinde boende i Kong David af Israels Palads, thi hellige er de Steder, hvor HERRENS Ark kommer.«
- 12 Nu ofrede Salomo Brændofre til HERREN paa HERRENS Alter, som han Havde bygget foran Forhallen,
- 13 idet han ofrede, som det efter Moses's Bud hørte sig til hver enkelt Dag, paa Sabbaterne, Nymaanedagene og Højtiderne tre Gange om Aaret, de usyrede Brøds Højtid, Ugernes Højtid og Løvhytternes Højtid.
- 14 Og efter den Ordning, hans Fader David havde truffet, satte han Præsternes Skifter til deres Arbejde og Leviterne til deres Tjeneste, til at synge Lovsangen og gaa Præsterne til Haande efter hver Dags Behov, ligeledes Dørvogterne efter deres Skifter til at holde Vagt ved de enkelte Porte; thi saaledes var den Guds Mand Davids Bud.
- 15 Og man fraveg ikke i mindste Maade Kongens Bud vedrørende Præsterne og Leviterne og Skatkamrene.
- 16 Saaledes fuldendtes hele Salomos Værk, fra den Dag Grundvolden lagdes til HERRENS Hus, til Salomo var færdig med HERRENS Hus.
- 17 Ved den Tid drog Salomo til Ezjongeber og Elot ved Edoms Kyst;
- 18 og Huram sendte ham Folk med Skibe og befarne Søfolk, der sammen med Salomos Folk sejlede til Ofir, hvor de hentede 450 Talenter Guld, som de bragte Kong Salomo.
-
-
King James Version (kjv)
- Afrikaans
- Arabic
- Armenian
- Basque
- Breton
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dutch
-
English
American King James Version (akjv) American Standard Version (asv) Basic English Bible (basicenglish) Douay Rheims (douayrheims) John Wycliffe Bible (c.1395) (wycliffe) King James Version (kjv) King James Version (1769) with Strongs Numbers and Morphology and CatchWords, including Apocrypha (without glosses) (kjva) Webster's Bible (wb) Weymouth NT (weymouth) William Tyndale Bible (1525/1530) (tyndale) World English Bible (web) Young's Literal Translation (ylt)
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malayalam
- Manx Gaelic
- Maori
- Myanmar Burmse
- Norwegian bokmal
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Thai
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
-
Danish (danish - 1.0.2)
2017-05-22Danish (da)
Danish translation of the Old Testament authorized in 1931 by the Danish King, with the New Testment being the authorized Danish version from 1907.
The NT is based on an entirely new OCR-scanning of an edition with Latin typographic (not Fraktur). The NT has subsequently been thoroughly proof-read and hand-corrected, and footnotes
as well as tables of contents for each chapter have been added.
The OT is based on an OCR-scan from the late 1980s, scanned from a typographically deficient
edition from 1933. OCR-scanning done and proof-read by a Danish pioneering couple with a heart
for media-missions. It was placed on the Internet by Søren Horn in the early 1990s, from
where it was picked up by Projekt Runeberg at Linköping University. Ulrik Sandborg-Petersen picked
up the text in the mid-2000's, and has since then hand-corrected literally thousands of OCR-mistakes
and paragraphing issues.
Both the OT and the NT retain the original orthography.
Errors and corrections should be sent to Ulrik Sandborg-Petersen via:
https://github.com/emg/- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Danish
- Distribution Abbreviation: danish
License
Public Domain
Source (OSIS)
https://github.com/emg/
- history_1.0
- (2017-05-20) Initial Release
- history_1.0.1
- (2017-5-21) added obsoletion notice to conf file for older module with same text from different source
- history_1.0.2
- (2022-08-09) Conf file corrections
- history_1..01
- (2017-05-22) Conf file corrections
Basic Hash Usage Explained
At getBible, we've established a robust system to keep our API synchronized with the Crosswire project's modules. Let me explain how this integration works in simple terms.
We source our Bible text directly from the Crosswire modules. To monitor any updates, we generate "hash values" for each chapter, book, and translation. These hash values serve as unique identifiers that change only when the underlying content changes, thereby ensuring a tight integration between getBible and the Crosswire modules.
Every month, an automated process runs for approximately three hours. During this window, we fetch the latest Bible text from the Crosswire modules. Subsequently, we compare the new hash values and the text with the previous ones. Any detected changes trigger updates to both our official getBible hash repository and the Bible API for all affected translations. This system has been operating seamlessly for several years.
Once the updates are complete, any application utilizing our Bible API should monitor the hash values at the chapter, book, or translation level. Spotting a change in these values indicates that they should update their respective systems.
Hash values can change due to various reasons, including textual corrections like adding omitted verses, rectifying spelling errors, or addressing any discrepancies flagged by the publishers maintaining the modules at Crosswire.
The Crosswire initiative, also known as the SWORD Project, is the "source of truth" for getBible. Any modifications in the Crosswire modules get reflected in our API within days, ensuring our users access the most precise and current Bible text. We pledge to uphold this standard as long as getBible exists and our build scripts remain operational.
We're united in our mission to preserve the integrity and authenticity of the Bible text. If you have questions or require additional information, please use our support system. We're here to assist and will respond promptly.
Thank you for your understanding and for being an integral part of the getBible community.
Favourite Verse
You should select one of your favourite verses.
This verse in combination with your session key will be used to authenticate you in the future.
This is currently the active session key.
Should you have another session key from a previous session.
You can add it here to load your previous session.